Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1532

reference: 167-tree-1
name: 1532
tree-preservation-order: undefined
167-tpo-1
uprn
address-text
point: POINT (-0.940705 50.865690)
geometry: MULTIPOLYGON (((-0.940634 50.865682,-0.940637 50.865696,-0.940647 50.865709,-0.940662 50.865719,-0.940682 50.865726,-0.940704 50.865728,-0.940726 50.865726,-0.940746 50.865720,-0.940762 50.865710,-0.940772 50.865698,-0.940776 50.865684,-0.940773 50.865670,-0.940763 50.865657,-0.940748 50.865647,-0.940728 50.865641,-0.940706 50.865638,-0.940684 50.865640,-0.940664 50.865646,-0.940648 50.865656,-0.940638 50.865669,-0.940634 50.865682)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL